Conversation
1. Added AddTTSAudioClip request and AddTTSAudioClip response for sending a text and its TTS configuration to the device（1621-1652）（2036-2041）（2418-2422）（2935-2943）. 2. Added complex types "TTS Audio" （1465-1485）for TTSConfiguration to support TTS function. It includes parameters Content, Language, VoiceType. 3. updated AudioClipCapabilities with TTSCapabilities（177-181）, and added complex types for TTSCapabilities（201-220）to indicate the device supports TTS function and its corresponding configuration. complex types TTSCapabilities includes MaxContentLength, TTSLanguage and TTSVoiceType. 4. Added simpleType TTSLanguage（220-231） and TTSVoiceType（232-238）.
1. Added detailed descriptions for AddTTSAudioClip operations, explaining their purpose, parameters, and responses.（2359-2416） 2. updated audio clip Capabilities with TTSCapabilities.（2698-2700）
update code line information for TTS function
correct some editorial errors
| <xs:documentation>Audio clip configuration to add.</xs:documentation> | ||
| </xs:annotation> | ||
| </xs:element> | ||
| <xs:element name="TTSConfiguration" type="tr2:TTSAudio"> |
There was a problem hiding this comment.
is TSSConfiguration for audio clip is returned in GetAudioClips API response? If not, how client can query TSSConfiguration for the given audio clip.
There was a problem hiding this comment.
No, there is no TTSConfiguration for audio clip returned in GetAudioClips API response. TTS configuration is just for device to convert a text to an audio clip, and it is stored in device just like other audio clips. So far, there is no use case for querying TTSConfiguration in GetAudioClips API response. If considering distinguish TTS audio clip and pre-recorded audio clip, client could consider to use element "name".
| <varlistentry> | ||
| <term>faults</term> | ||
| <listitem> | ||
| <para role="param">env:Receiver - ter:Action - ter:MaxAudioClipLimit</para> |
There was a problem hiding this comment.
I propose to rename ter:MaxAudioClipLimit to ter:MaxAudioClip to unifor with similar errors for other functions
There was a problem hiding this comment.
MaxAudioClipLimit parameter was added as part of Audio Clip Management feature and the technical specification for this feature is released in ONVIF V25.06. Changing the parameter name now can cause backward combability issue.
| </xs:complexType> | ||
| <!--===============================--> | ||
| <!--=============TTS Capability=================--> | ||
| <xs:complexType name="TTSCapabilities"> |
There was a problem hiding this comment.
Should we also have the maximum number of clips? Since the device can return ter:MaxAudioClip , the limit should be available as a capability
There was a problem hiding this comment.
TTS audio clip is actually an audio clip, there is an attribute"MaxAudioClipLimit" in AudioClipCapabilities already, it can cover TTS audio clip.
Updated the description of the AddTTSAudioClip operation to clarify the parameters and response. Updated the description of TTScapabilities.
|
@Peggy0422 I do not understand the relationship between this PR, #692 and #694 . What is the right one? |
|
Closing this PR since already a new PR is open for the same feature. |
4 participants
To support audio product with TTS function, serveral operations should be done, which are:
TTSCapabilities(Optional): Add complex type TTSCapabilities to the exsiting complex Type "AudioClipCapabilities" as optional, to indicate whether the device is capable of TTS function and the detailed configuration if so.
parameter:
MaxContentLength: the Max length of the content in a text file that device could convert into an audio clip;
TTSLanguage: indicates what languages the device supports for client to choose to perform TTS.
TTSVoiceType: indicates what types of voice that device supports when device play an audio clip converted from a text.
Add “AddTTSAudioClip”and "AddTTSAudioClipResponse"element: To send a text and its configuartion to device that supports TTS, so that device could convert it into an audio clip and play it according to Configuration and TTS Configuration.
Parameter:
Token(Optional): token for the audio clip.
Configuration: Audio clip configuration to add, reference to Configuration for AddAudioClip.
TTSConfiguration: The configuration for the TTS audio clip to add, it specifys the audio content, language and voice type when device play this audio clip.
Reponse:
Token: Unique token of the TTS audio clip to be uploaded.
media2.wsdl
complex types TTSCapabilities includes MaxContentLength, TTSLanguage and TTSVoiceType.
media2.xml and documentation
ONVIF-Media2-Service-Spec-TTS update.docx